home *** CD-ROM | disk | FTP | other *** search
- Path: mail2news.demon.co.uk!hpl3sn03.cern.ch
- From: Dan Pop <danpop@mail.cern.ch>
- Newsgroups: comp.lang.c
- Subject: Re: What does the -O option do???!!!
- Date: Sun, 11 Feb 1996 00:32:18 +0100
- Organization: CERN European Lab for Particle Physics
- Message-ID: <9602102332.AA09466@dxmint.cern.ch>
- References: <4ehger$cj9@mark.ucdavis.edu> <4emlsq$odt@airdmhor.gen.nz> <pronet01.34.003B9BB5@indirect.com> <823827008snz@genesis.demon.co.uk> <4fiphrINNrvr@keats.ugrad.cs.ubc.ca>
- X-NNTP-Posting-Host: hpl3sn03.cern.ch
- X-Newsreader: NN version 6.5.0 #7 (NOV)
- X-Mail2News-Path: dxmint.cern.ch!hpl3sn03.cern.ch
-
- c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku) writes:
-
- >... as long as it is not hard-coded to treat identifiers like "free" specially.
-
- A compiler is free to treat identifiers like "free" specially after the
- relevant header has been included.
-
- >If you write your own free() with different semantics, you would not want the
- >compiler messing with that.
-
- If you write your own free() you invoke undefined behaviour and you can't
- expect the compiler to behave in a sensible way. The implementation
- namespace is a big taboo in C.
-
- >It's just another function, after all.
-
- No, it isn't. Have a look at the standard.
-
- >Some
- >compilers have special directives that you can apply to function prototypes
- >that give a hint to the compiler (for example, hints like "this function does
- >not return, so you may treat client code accordingly").
-
- Once you do this you have already left the realms of the C language.
-
- Dan
- --
- Dan Pop
- CERN, CN Division
- Email: danpop@mail.cern.ch
- Mail: CERN - PPE, Bat. 31 R-004, CH-1211 Geneve 23, Switzerland
-